Skip to content

Conversation

@sighphyre
Copy link
Member

Harvests out the evaluation logic for the UnleashClient in prep for building an async variant without a ton of copy paste.

The only change that I've made here is that the evaluation now needs to know the run state of the client itself to determine whether it's hydrated or not (client still needs to know that for lifecycle). Ideally this would get owned by the Yggdrasil engine at some point but right now I want to keep this as small and light as possible

@coveralls
Copy link

Pull Request Test Coverage Report for Build 18994751008

Details

  • 126 of 135 (93.33%) changed or added relevant lines in 4 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.07%) to 93.776%

Changes Missing Coverage Covered Lines Changed/Added Lines %
UnleashClient/core/contracts.py 10 13 76.92%
UnleashClient/core/client.py 99 105 94.29%
Totals Coverage Status
Change from base Build 18272747945: -0.07%
Covered Lines: 678
Relevant Lines: 723

💛 - Coveralls

@sighphyre sighphyre self-assigned this Nov 4, 2025
@FredrikOseberg FredrikOseberg moved this from New to In Progress in Issues and PRs Nov 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

2 participants